Systems and methods for detecting a sitting duck scenario

ABSTRACT

Systems and methods for detecting a sitting duck scenario of a vehicle on or near a road are disclosed. The current location and speed of the vehicle are used for different comparisons and/or determinations, including a comparison to road-specific information to determine whether the vehicle is in a particular proximity of a highway, and a determination whether the vehicle has been stationary continuously for at least a specified duration. Additional comparisons and/or determinations may be used. If such an occurrence has been detected, one or more notifications are generated, and provided to one or more of the vehicle operator and/or a remote computing server.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods for detectingcertain traffic scenarios involving stationary vehicles. For example,detections may involve stalled, parked, or inoperative vehicles, whichmay be situated proximate or adjacent to actual and/or potential othertraffic.

BACKGROUND

Monitoring vehicle operations is known, in particular for the occurrenceof events such as speeding or collisions. Video monitoring of vehiclesor vehicle operators during operation is known.

SUMMARY

One aspect of the present disclosure relates to a system configured fordetecting a sitting duck scenario of a vehicle on or near a road, thevehicle being operated by a vehicle operator. The system may include oneor more hardware processors configured by machine-readable instructions.The system may be configured to obtain output signals conveyinginformation pertaining to the vehicle and to operation of the vehicle.The system may be configured to determine a current speed of thevehicle. The determination of the current speed is based on the outputsignals. The system may be configured to determine a current location ofthe vehicle. The determination of the current location is based on theoutput signals. The system may be configured to obtain road-specificinformation for one or more roads near the current location of thevehicle. The road-specific information may include: i) one or more typesof road pertaining to the one or more roads near the current location ofthe vehicle, and ii) one or more types of geographical locationinformation pertaining to the one or more roads. The system may beconfigured to make a first determination whether the current location ofthe vehicle is on or within a particular proximity of highways. Thehighways are public roads heading in one or more directions, having oneor more lanes heading in the one or more directions. The one or morelanes are intended to include vehicular traffic. The first determinationis based on the current location and the obtained road-specificinformation. The particular proximity is determined based on a distancethreshold of 100 feet or less. The system may be configured to make asecond determination whether the vehicle has been stationarycontinuously for at least a specified duration, wherein the specifiedduration is at least 5 minutes. The system may be configured to detectan occurrence of a particular vehicle event responsive to a combinationof at least two determinations. The at least two determinations includethe first determination that the current location of the vehicle is onor within the particular proximity of highways and the seconddetermination that the vehicle has been stationary continuously for atleast the specified duration. Responsive to detection of the occurrenceof the particular vehicle event, the system may be configured togenerate one or more notifications regarding the particular vehicleevent. The system may be configured to provide the one or morenotifications to one or more of the vehicle operator and/or a remotecomputing server.

Another aspect of the present disclosure relates to a method fordetecting a sitting duck scenario of a vehicle on or near a road, thevehicle being operated by a vehicle operator. The method may includeobtaining output signals conveying information pertaining to the vehicleand to operation of the vehicle. The method may include determining acurrent speed of the vehicle. The determination of the current speed isbased on the output signals. The method may include determining acurrent location of the vehicle. The determination of the currentlocation is based on the output signals. The method may includeobtaining road-specific information for one or more roads near thecurrent location of the vehicle. The road-specific information mayinclude: i) one or more types of road pertaining to the one or moreroads near the current location of the vehicle, and ii) one or moretypes of geographical location information pertaining to the one or moreroads. The method may include making a first determination whether thecurrent location of the vehicle is on or within a particular proximityof highways. The highways are public roads heading in one or moredirections, having one or more lanes heading in the one or moredirections. The one or more lanes are intended to include vehiculartraffic. The first determination is based on the current location andthe obtained road-specific information. The particular proximity isdetermined based on a distance threshold of 100 feet or less. The methodmay include making a second determination whether the vehicle has beenstationary continuously for at least a specified duration, wherein thespecified duration is at least 5 minutes. The method may includedetecting an occurrence of a particular vehicle event responsive to acombination of at least two determinations. The at least twodeterminations include the first determination that the current locationof the vehicle is on or within the particular proximity of highways andthe second determination that the vehicle has been stationarycontinuously for at least the specified duration. Responsive todetection of the occurrence of the particular vehicle event, the methodmay include generating one or more notifications regarding theparticular vehicle event. The method may include providing the one ormore notifications to one or more of the vehicle operator and/or aremote computing server.

As used herein, any association (or relation, or reflection, orindication, or correspondency) involving servers, processors, clientcomputing platforms, vehicles, vehicle operators, roads, types of roads,lanes, sensors, locations, directions, determinations, detections,durations, goals, recommendations, notifications, vehicle events, and/oranother entity or object that interacts with any part of the systemand/or plays a part in the operation of the system, may be a one-to-oneassociation, a one-to-many association, a many-to-one association,and/or a many-to-many association or N-to-M association (note that N andM may be different numbers greater than 1).

As used herein, the term “obtain” (and derivatives thereof) may includeactive and/or passive retrieval, determination, derivation, transfer,upload, download, submission, and/or exchange of information, and/or anycombination thereof. As used herein, the term “effectuate” (andderivatives thereof) may include active and/or passive causation of anyeffect, both local and remote. As used herein, the term “determine” (andderivatives thereof) may include measure, calculate, compute, estimate,approximate, generate, and/or otherwise derive, and/or any combinationthereof.

These and other features, and characteristics of the present technology,as well as the methods of operation and functions of the relatedelements of structure and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the invention. As usedin the specification and in the claims, the singular form of “a”, “an”,and “the” include plural referents unless the context clearly dictatesotherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured for detecting a sitting duckscenario of a vehicle on or near a road, the vehicle being operated by avehicle operator, in accordance with one or more implementations.

FIG. 2 illustrates a method for detecting a sitting duck scenario of avehicle on or near a road, the vehicle being operated by a vehicleoperator, in accordance with one or more implementations.

FIGS. 3 and 4 illustrate exemplary roads as may be used by a systemconfigured for detecting a sitting duck scenario of a vehicle on or neara road, the vehicle being operated by a vehicle operator, in accordancewith one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured for detecting a sitting duckscenario of a vehicle on or near a road, the vehicle being operated by avehicle operator, in accordance with one or more implementations. Asused herein, the term “sitting duck” may refer to a vehicle that hasbeen stationary continuously for at least a specified duration (in someimplementations of at least five minutes) on or within a particularproximity of the nearest road. Additional conditions to specify thisterm may be considered within the scope of this disclosure. In someimplementations, the vehicle's engine may be on or off. Typically,vehicles stuck in traffic or parked legally are not considered assitting duck. In some implementations, the term “shoulder” of a road maybe defined as an emergency stopping lane, typically on the right of theright-most lane in countries that drive on the right, and typically wideenough to accommodate a stopped vehicle without impeding the flow oftraffic. Vehicles in a lane, on the shoulder of the road, and/orpartially in a lane and partially on the shoulder may be considered assitting duck. In some implementations, a sitting duck scenario may becaused due to a vehicle being out of fuel. In some implementations, asitting duck scenario may be caused due to mechanical and/or electricalmalfunction. In some implementations, a sitting duck scenario may becaused due to a collision and/or other accident. In someimplementations, a sitting duck scenario may be caused due to a changeof drivers, a driver sleeping, resting, and/or taking a break, and/orother circumstances initiated by a driver. Other causes and combinationsof multiple causes may be considered in detecting a sitting duckscenario. From the perspective of a driver, truck owner, fleet manager,and/or other stakeholder, vehicles in a sitting duck scenario may be atrisk, e.g., due to other traffic. Accordingly, system 100 is configuredto detect these scenarios and provide notifications (e.g., warnings)related to these detected scenarios. In some implementations, a vehiclethat uses system 100 may be configured to take certain actionsresponsive to these detected scenarios, as described elsewhere in thisdisclosure. In some implementations, system 100 may include the vehicleitself, whereas in other implementations system 100 may exclude thevehicle itself.

The roads vehicles are on or near may include public roads, privateroads, and/or other types of roads. By way of non-limiting example, thetypes of public roads may include highways having one or more trafficlanes heading in one or more directions. Individual roads may head intoone or more directions of travel. In some implementations, the roads mayinclude one or more traffic lanes in each direction of travel. Trafficlanes may be intended to include vehicular traffic. In someimplementations, individual roads may have (direction-based) centerlinesbetween traffic lanes heading in opposite directions. In someimplementations, individual roads may have (geometry-based) centerlinesin the geometric center of all the traffic lanes that form the entireroad in all directions. In some implementations, highways may havecontrolled entries and/or exits, such as (metered) on-ramps andoff-ramps. In some implementations, highways may have a dividing stripbetween traffic in opposite directions. In some implementations,highways may have certain speed limits, such as, for example, at least40 mph, at least 45 mph, at least 50 mph, at least 55 mph, at least 60mph, at least 65 mph, and/or other ranges of speed limits. In someimplementations, highways may be characterized by a lack of trafficlights. In some implementations, the classification of whether a road isa highway may be under government control. In some implementations, theclassification of roads may include roads being classified as primaryroads, secondary roads, rural roads, city roads, and/or other types ofroads. For example, a government-controlled entity may provideroad-specific information, e.g., an online database, that includes thetypes of road for multiple roads in a particular geographical area, suchas, by way of non-limiting example, a state, a county, a city, amunicipal entity, and/or other particular geographical areas.

In some implementations, system 100 may include one or more of servers102, electronic storage 130, a set of sensors 108, network(s) 13, clientcomputing platform(s) 104, external resources 128, a remote computingserver 129, and/or other components. System 100 and/or componentsthereof may be carried and/or otherwise supported by one or morevehicles (e.g., a first vehicle, a second vehicle, a third vehicle, andso forth), including but not limited to a vehicle 12. Operation ofsystem 100 may be described in the context of a particular vehicle,e.g., vehicle 12, but this is not intended to be limiting. In someimplementations, system 100 may detect sitting duck scenarios for afleet of multiple vehicles. In some implementations, individual vehicles(e.g., vehicle 12) may carry and/or otherwise support system 100 and/orcomponents thereof. Server(s) 102 may be configured to communicate withone or more client computing platforms 104 according to a client/serverarchitecture and/or other architectures. Client computing platform(s)104 may be configured to communicate with other client computingplatforms via server(s) 102 and/or according to a peer-to-peerarchitecture and/or other architectures. Users may access system 100 viaclient computing platform(s) 104.

Individual vehicles may include a set of resources for informationgathering, data processing, and/or electronic storage, including but notlimited to persistent storage. Individual vehicles may include sensors(e.g., set of sensors 108 configured to generate and/or otherwise gatherdata, such as output signals). In some implementations, individualvehicles may be configured to detect vehicle events, e.g., based onoutput signals generated by set of sensors 108. As used herein, the term“vehicle event” may include occurrences of events involving one or morevehicles. As such, detection of vehicle events may include gatheringinformation by monitoring the operation of one or more vehicles,including but not limited to information related to current or pastvehicle speeds, current or current location, and/or other informationpertinent to detecting of vehicle events, particularly occurrences ofsitting duck scenarios.

In some implementations, operation of vehicle 12 may be actively andprimarily controlled by a vehicle operator (i.e., a human operator). Insuch a case, a non-human vehicle operator may take over (or be requestedto take over) control of the vehicle in certain circumstances. In someimplementations, operation of vehicle 12 may be actively and primarilycontrolled by an autonomous driving algorithm (also referred to as analgorithmic vehicle operator, or a non-human vehicle operator). In sucha case, a human vehicle operator may take over (or be requested to takeover) control of the autonomous driving algorithm, e.g., responsive toextreme and/or unconventional driving scenarios, or responsive to afailure or error-condition of the autonomous driving algorithm. In someimplementations, a human vehicle operator and an autonomous drivingalgorithm may form a team that controls operations of vehicle 12together.

Set of sensors 108 may be configured to generate output signalsconveying information related to (operation of) vehicle 12, a locationof vehicle 12, a vehicle operator of vehicle 12, and/or a context ofvehicle 12 (e.g., related to the surroundings of vehicle 12). In someimplementations, set of sensors 108 may be carried by vehicle 12. Insome implementations, one or more sensors in set of sensors 108 may beexternal to vehicle 12, such as roadside sensors, sensors embedded inthe surface of a road, sensors carried by other vehicles, and/or othersensors. Although set of sensors 108 is depicted in FIG. 1 as a singleelement, this is not intended to be limiting. In some implementations,set of sensors 108 may be configured to generate output signalscontinuously, in an on-going manner, and/or at regular or irregularintervals during operation of vehicle 12.

Information related to the operation of vehicle 12 may include feedbackinformation from one or more of the mechanical systems (not shown inFIG. 1) of vehicle 12, and/or other information. The mechanical systemsof vehicle 12 may include, for example, the engine, the drive train, thelighting systems (e.g., headlights, brake lights), the braking system,the transmission, fuel delivery systems, and/or other mechanicalsystems. The mechanical systems of vehicle 12 may include one or moremechanical sensors, electronic sensors, and/or other sensors thatgenerate the output signals (e.g., seat belt sensors, tire pressuresensors, etc.). In some implementations, at least one of sensors 14 maybe a vehicle system sensor included in an Engine Control Module (ECM)system of vehicle 12.

In some implementations, set of sensors 108 may generate output signalsconveying information related to a vehicle operator of vehicle 12, suchas visual information, motion-related information, position-relatedinformation, biometric information, medical information, and/or otherinformation. In some implementations, set of sensors 108 may include oneor more sensors configured to generate output signals that conveyinformation related to biological activity of the vehicle operator. Insome implementations, one or more sensors may be wearable by the vehicleoperator. In some implementations, one or more sensors may be placed inphysical proximity to the vehicle operator to facilitate monitoring thebiological activity of the vehicle operator. The information related tothe biological activity of the vehicle operator may include heart rate,respiration rate, verbal expressions, responses to conditions in thephysical environment in and/or around vehicle 12, and/or othercharacteristics of or information about the vehicle operator.

In some implementations, set of sensors 108 may generate output signalsconveying information related to the context of vehicle 12, such asinformation related to the environment in and/or around vehicle 12. Thevehicle environment may include spaces in and around an interior and anexterior of vehicle 12. The information related to the context ofvehicle 12 may include information related to movement of vehicle 12, anorientation of vehicle 12, a geographic position of vehicle 12, aspatial position of vehicle 12 relative to other objects, a tilt angleof vehicle 12, an inclination/declination angle of vehicle 12, and/orother information. In some implementations, the output signals conveyingthe information related to the context of vehicle 12 may be generatedvia non-standard aftermarket sensors installed in vehicle 12. Set ofsensors 108 may include, for example, one or more of an image sensor, acamera, a video camera, a microphone, an accelerometer, a gyroscope, ageolocation sensor (e.g., a Global Positioning System or GPS device), aradar detector, a magnetometer, lidar (e.g., for measuring distance of aleading vehicle), an altimeter (e.g. a sonic altimeter, a radaraltimeter, and/or other types of altimeters), a barometer, amagnetometer, a pressure sensor (e.g. a static pressure sensor, adynamic pressure sensor, a pitot sensor, etc.), a thermometer, aninertial measurement sensor, a tilt sensor, a motion sensor, a vibrationsensor, an ultrasonic sensor, an infrared sensor, a light sensor, adepth sensor, an air speed sensor, a ground speed sensor, an altitudesensor, medical sensors (including but not limited to blood pressuresensor, pulse oximeter, heart rate sensor, etc.), degree-of-freedomsensors (e.g. 6-DOF and/or 9-DOF sensors), a compass, and/or othersensors. As used herein, the term “motion sensor” may include one ormore sensors configured to generate output conveying information relatedto position, location, distance, motion, movement, acceleration, and/orother motion-based parameters. Output signals generated by individualsensors (and/or information based thereon) may be stored and/ortransferred in electronic files. In some implementations, output signalsmay be transferred as one or more streams of data.

As used herein, the terms “camera” and/or “image sensor” may include anydevice that captures image information, including but not limited to asingle lens-based camera, a camera array, a solid-state camera, amechanical camera, a digital camera, an image sensor, a depth sensor, aremote sensor, a lidar, an infrared sensor, a (monochrome) complementarymetal-oxide-semiconductor (CMOS) sensor, an active pixel sensor, and/orother sensors. Individual sensors may be configured to captureinformation, including but not limited to visual information, videoinformation, audio information, geolocation information, orientationand/or motion information, depth information, distance information,and/or other information. Information captured by one or more sensorsmay be marked, timestamped, annotated, and/or otherwise processed suchthat information captured by other sensors can be synchronized, aligned,annotated, and/or otherwise associated therewith. For example, videoinformation captured by an image sensor may be synchronized withinformation captured by an accelerometer or other sensor. In someimplementations, set of sensors 108 may include multiple cameraspositioned around the vehicle and synchronized together to provide a360-degree view of the inside of a vehicle and/or a 360-degree view ofthe outside of a vehicle. In some implementations, an image sensor maybe integrated with electronic storage such that captured information maybe (processed and) stored in the integrated embedded storage. In someimplementations, a sensor may be configured to transfer capturedinformation to remote electronic storage media, e.g. through “thecloud.”

Server(s) 102 may be configured by machine-readable instructions 106.Machine-readable instructions 106 may include one or more instructioncomponents. The instruction components may include computer programcomponents. The instruction components may include one or more of aparameter determination component 110, a road-specific informationcomponent 112, a proximity component 114, a stationary component 116, adetection component 118, a notification component 120, a combinatorialcomponent 122, an environmental component 124, an interface component126, and/or other instruction components.

Parameter determination component 110 may be configured to determineparameters. For example, the parameters may pertain to the operation ofvehicle 12, the current speed of vehicle 12, the current location ofvehicle 12, the context of or pertaining to vehicle 12, environmentalconditions in or near vehicle 12, and/or other parameters. In someimplementations, parameter determination component 110 may be configuredto obtain information. The obtained information may include one or moreof output signals generated by set of sensors 108, parameters determinedbased on output signals generated by set of sensors 108, informationfrom external resources 128, and/or other information. For example, insome implementations, parameter determination component 110 may beconfigured to obtain output signals from set of sensors 108 that conveyinformation pertaining to vehicle 12 and to the operation of vehicle 12,and further configured to determine a current speed of vehicle 12 basedon the obtained output signals. In some implementations, parameterdetermination component 110 may be configured to obtain the currentspeed of vehicle 12. For example, in some implementations, parameterdetermination component 110 may be configured to obtain output signalsfrom set of sensors 108 that convey information pertaining to thecurrent location of vehicle 12, and further configured to determine thecurrent location of vehicle 12 based on the obtained output signals. Insome implementations, parameter determination component 110 may beconfigured to obtain the current location of vehicle 12. In someimplementations, parameter determination component 110 may be configuredto determine and/or obtain the current orientation and/or heading ofvehicle 12, either relative to the nearest road, or using an absoluterepresentation such as a real-world coordinate system.

Road-specific information component 112 may be configured to obtainroad-specific information. For example, the road-specific informationmay include information for one or more roads near the current locationof vehicle 12 (e.g., as determined and/or obtained by parameterdetermination component 110). In some implementations, the road-specificinformation may include one or more of the types of roads near thecurrent location of vehicle 12, the types of geographical locationinformation of the roads near the current location of vehicle 12, and/orother road-specific information. For example, the types of road mayinclude public roads, private roads, and/or other types of roads. Insome implementations, the types of roads may include highways,expressways, city streets, residential streets, and/or other types ofroads. In some implementations, the types of roads may include 2-lanehighways, 4-lane highways, 6-lane highways, 8-lane highways, multi-lanehighways, and/or other types of roads. In some implementations,road-specific information may include how many traffic lanes are headingin each direction, how many traffic lanes in total form the entire roadin both directions, and/or other specific information regarding one ormore traffic lanes of a particular road. For example, in someimplementations, the road-specific information may specify the numberand width of the individual traffic lanes of a particular road. In someimplementations, road-specific information may include local speedlimits. In some implementations, road-specific information may beobtained from one or more external databases, e.g., from one or moreexternal resources 128.

In some implementations, geographical location information may specifyand/or represent the geographical location of a specific road. Forexample, the geographical location of a particular road may include GPSinformation (e.g., a set of GPS coordinates). For example, in someimplementations, the road may be assumed to approximate straight linesbetween adjacent GPS coordinates (e.g., in a set or sequence of GPScoordinates). In some implementations, the geographical information mayindicate the (direction-based or geometry-based) centerline of an entiremulti-lane multi-directional road. In some implementations, thegeographical location of a particular road may include multiple sets ofGPS coordinates, using individual sets for individual directions oftravel or for individual lanes. In some implementations, thegeographical location of a particular road may include two sets of GPScoordinates such that the road may be assumed to exist betweenboundaries defined by each of the sets. For example, the first set maydefine the boundary on the outside of the right-most traffic laneheading in a first direction (e.g., North), and the second set maydefine the boundary on the outside of the right-most traffic laneheading in a second direction (e.g., South), such that this particularroad is located between the first and second boundaries. In someimplementations, a boundary may define the edge of a traffic laneintended to include vehicular traffic. In some implementations, aboundary may define the edge of the shoulder of road. The particulartype of the geographical location information may indicate what thegeographical location information represents and/or how it should beinterpreted in relation to the geographical location of a particularroad. For example, for a first type of 2-lane road, a first type ofgeographical location information may indicate a particular centerline.For example, for a second type of 2-lane road, a second type ofgeographical location information may indicate the boundaries of theroad (e.g., excluding emergency lanes). For example, for a third type of2-lane road, a third type of geographical location information mayindicate individual (geometry-based) centerlines for each of the lanes.Likewise, many different types of geographical location information maybe used to represent the geographical location of a specific 4-lanehighway, 6-lane highway, 8-lane highway, and so forth. In someimplementations, a particular road may have a different number oftraffic lanes heading in opposite directions. In such cases, thedirection-based centerline between the traffic lanes heading in oppositedirections (e.g., North and South) may not be in the geometric center ofthe outer boundaries of the entire road.

Proximity component 114 may be configured to make determinationsregarding the current location of vehicle 12 in relation to one or moreroads near vehicle 12. In some implementations, proximity component 114may be configured to determine which particular road is closest orproximate to the current location of vehicle 12, and/or what type ofroad is closest or proximate to the current location of vehicle 12. Forexample, one determination may be whether vehicle 12 is in a lane of ahighway. For example, one determination may be whether any part ofvehicle 12 is in a lane of a highway. For example, one determination maybe whether vehicle 12 is proximate or adjacent to a lane of a highway.This type of determination may depend of the type of vehicle, thelocation of one or more GPS sensors on vehicle 12, the heading and/ororientation of vehicle 12 relative to the heading of the nearest trafficlane, and/or other information. For example, one determination may bewhether vehicle 12 is within a particular proximity of a highway. Forexample, the particular proximity may be 25 feet, 50 feet, 75 feet, 100feet, 150 feet, and/or another distance. For example, one determinationmay be whether any part of vehicle 12 is within a particular proximityof a highway. In some implementations, one determination may be whethervehicle 12 is within a particular proximity of a road that has a speedlimit of at least 40 mph, 45 mph, 50 mph, 55 mph, 60 mph, 65 mph, and/orother ranges of speed limits. In some implementations, the headingand/or orientation of vehicle 12 relative to the heading of the nearesttraffic lane may be based on GPS information. In some implementations,the heading and/or orientation of vehicle 12 relative to the heading ofthe nearest traffic lane may be determined based on processed videoinformation from set of sensors 108.

In some implementations, the particular proximity (as used by proximitycomponent 114) may depend dynamically on one or more of the type of thenearest road, the number and type of traffic lanes, the type ofavailable geographical location information for the nearest road, thelocal speed limit for the nearest road, and/or other road-specificinformation. For example, in some implementations, the particularproximity used to determine whether vehicle 12 is within the particularproximity of a highway may be 25 feet for 2-lane roads and 50 feet for4-lane roads (such that the particular proximity depends dynamically onthe number of lanes for the nearest road). In some implementations,certain types of roads, such as on-ramps to highways and off-ramps ofhighways, may be excluded from consideration for determinations byproximity component 114 (such that a vehicle is not considered within aparticular proximity of a highway in case the vehicle is on an on-rampor off-ramp). For example, in some implementations, the particularproximity used to determine whether vehicle 12 is within the particularproximity of a highway may be 25 feet for roads for which the locationof the boundaries are known/available and 50 feet for roads for whichonly the centerline is known, and the location of the boundaries is notavailable (such that the particular proximity depends dynamically on thetype of available geographical location information for the nearestroad). For example, in some implementations, the particular proximityused to determine whether vehicle 12 is within the particular proximityof a highway may be 25 feet for roads for which the location of theshoulder is known/available and 50 feet for roads for which the locationof the shoulder is not available (or roads that have no shoulder). Insome implementations, the particular proximity may dynamically depend ona combination of multiple factors, such as the number of lanes and thetype of available geographical location information, and/or otherfactors). In some implementations, the particular proximity maydynamically depend on vehicle-specific information. For example, theused particular proximity may be greater for a larger truck and smallerfor a small truck or personal vehicle. For example, the used particularproximity may be greater for a truck carrying combustible goods andsmaller for a truck carrying non-combustible goods. In someimplementations, the particular proximity may dynamically depend onfleet-specific information. For example, the used proximity may begreater for any vehicle in a first fleet of vehicles and smaller for anyvehicle in a second fleet of vehicles. For example, a fleet managerand/or other stakeholder may enter and/or select information, via a userinterface, that is used to (dynamically) determine the particularproximity.

By way of non-limiting example, FIG. 3 illustrates an exemplary road 300as may be used by system 100. As depicted, road 300 is a 4-lane highwaythat includes two lanes in each direction, divided by a dividing strip305. Lanes 301 and 302 are heading in the same direction. Lanes 303 and304 are heading in the opposite direction as lanes 301 and 302. Vehicle12 is partially on a lane 302. System 100 (depicted in FIG. 1) may beconfigured to determine that vehicle 12 is within a particular proximity(of, say, 25 feet) of road 300, because at least part of vehicle 12 isin lane 302.

By way of non-limiting example, FIG. 4 illustrates an exemplary road 400as may be used by system 100. As depicted, road 400 is a 6-lane highwaythat includes three lanes in each direction, divided by a dividing strip410. Lanes 401, 402, and 403 are heading in the same direction. Lanes404, 405, and 406 are heading in the opposite direction as lanes 401,402, and 403. Vehicle 12 is not on any of the lanes. System 100(depicted in FIG. 1) may be configured to determine that vehicle 12 iswithin a particular proximity (of, say, 25 feet) of road 400, because atleast part of vehicle 12 is within 25 feet of lane 403. In someimplementations, system 100 may be configured to determine that vehicle12 is stationary in an orientation parallel to road 400 (e.g., thedifferential angle between the orientation of vehicle 12 and lane 403 isless than 30 degrees, which may be considered parallel).

Referring to FIG. 1, stationary component 116 may be configured todetermine whether vehicle 12 is or has been stationary. In someimplementations, determinations regarding vehicle 12 being stationarymay be based on the current speed of vehicle 12 (e.g., the current speedbeing zero). In some implementations, stationary component 116 may beconfigured to determine whether vehicle 12 has been stationarycontinuously for at least a specified duration. In some implementations,the specified duration may be at least 2 minutes, 3 minutes, 5 minutes,10 minutes, 15 minutes, 20 minutes, and/or another specified duration.In some implementations, the specified duration may vary based on otherfactors, including but not limited to time of day, weather conditions,visibility conditions, traffic conditions, and/or other factors. In someimplementations, a determination whether vehicle 12 is stationaryincludes a requirement that the engine of vehicle 12 is turned off. Insome implementations, no requirement regarding the engine is used todetermine whether vehicle 12 is stationary. In some implementations, adetermination whether vehicle 12 is stationary includes a requirementthat vehicle 12 itself is turned off. In some implementations, norequirement regarding vehicle 12 being turned off is used to determinewhether vehicle 12 is stationary. In some implementations, adetermination whether vehicle 12 is stationary may include adetermination that vehicle 12 is inoperable.

Detection component 118 may be configured to detect vehicle events,including but not limited to vehicle events of vehicle 12. In someimplementations, detections by detection component 118 may be based onone or more of the current operation of vehicle 12, informationpertaining to vehicle 12, current parameters of vehicle 12 (e.g., asdetermined by parameter determination component 110), road-specificinformation, determinations by other components of system 100, and/orother factors, as well as combinations thereof. For example, aparticular vehicle event may be detected based on a combination ofmultiple determinations (e.g., at least two determinations, or at leastthree determinations, or at least more than three determinations). Forexample, a particular vehicle event may be detected based on acombination of a first determination that the current location ofvehicle 12 is within a particular proximity of the nearest highway, anda second determination that vehicle 12 has been stationary continuouslyfor at least a specified duration. For example, a particular vehicleevent may be detected based on a combination of the first determination,the second determination, and a third determination that vehicle 12 isnot in a designated area for stopping vehicles. In some implementations,a combination may be used of the first determination, the seconddetermination, and another determination that vehicle 12 is stationaryin an orientation that is parallel to the nearest road (e.g., thedifferential angle between the orientation of vehicle 12 and the nearestroad is less than, e.g., 20, 30, and/or 45 degrees, which may beconsidered parallel). In some implementations, a combination may be usedof the first determination, the second determination, and anotherdetermination that vehicle 12 was traveling at least a particular speed(e.g., 50 mph), for at least a particular duration (e.g., 5 minutes), ina particular time frame (e.g., a duration of at least 10 minutesimmediately preceding the determination that vehicle 12 has becomestationary). Other combinations and the use of additional determinationsare considered within the scope of this disclosure.

In some implementations, designated areas for stopping vehicles mayinclude different types of geographical areas, including one or more ofrest stops, travel centers, truck stops, parking areas, vista points,over-night stay locations, ‘stop-n-park’ locations, ‘park-n-ride’locations, common stop areas (e.g., these may have been identifiedand/or designated based on historical usage by other vehicles,crowd-sourcing by drivers, and/or through other information-gatheringtechniques), fueling stations, combinations of fueling stations andrestaurants, other combinations that include one or more fuelingstations, and/or other designated areas. In some implementations, adesignated area may be indicated and/or defined by a polygon, e.g.,using GPS coordinates and/or other real-world coordinates. In someimplementations, information regarding designated areas for stoppingvehicles may be obtained from external databases.

In some implementations, a determination that a particular vehicle is ina particular designated area for stopping vehicles may be implemented asthe entirety of the particular vehicle being completely within thepolygon that defines and/or indicates the particular designated area. Insome implementations, a determination that a particular vehicle is in aparticular designated area for stopping vehicles may be implemented asat least half of the particular vehicle being within the polygon thatdefines and/or indicates the particular designated area. In someimplementations, a determination that a particular vehicle is near aparticular designated area for stopping vehicles may be implemented asall or some of the particular vehicle being within a particularproximity of the polygon that defines and/or indicates the particulardesignated area.

Notification component 120 may be configured to generate notifications,including but not limited to notifications regarding detected vehicleevents. In some implementations, notification component 120 may beconfigured to provide notifications to one or more of a vehicle operatorof vehicle 12, remote computing server 129, one or more manualreviewers, one or more fleet managers, one or more supervisors of thevehicle operator of vehicle 12, and/or other stakeholders. In someimplementations, notification component 120 may be configured togenerate reports that include information regarding detected vehicleevents. For example, notification component 120 may be configured toprovide a notification to the vehicle operator of vehicle 12 (e.g.,through a user interface within vehicle 12, or through a clientcomputing device associated with the vehicle operator) that warns thevehicle operator regarding a detected vehicle event and/or provides asuggestion to move vehicle 12 further from the nearest road.

Combinatorial component 122 may be configured to make combinations ofmultiple determinations (e.g., 2, 3, 4, or more determinations, eithersequentially, simultaneously, and/or arranged in a particular pattern).For example, in some implementations, a combination may include twodeterminations that occur at substantially the same time, and/or withina short window of time of 1, 2, 3, 4, 5, or more minutes. For example,in some implementations, a combination may include an initial twodeterminations that occur at substantially the same time, followed byone or more determinations that are made within a particular window oftime after the initial two determinations. More elaborate sequences ofcombinations are considered within the scope of this disclosure. Forexample, a combination may include a first determination that vehicle 12was traveling at least, say, 50 mph for at least, say, 5 minutes in aparticular time frame. The particular time frame may include a durationof at least, say, 10 minutes immediately preceding the specifiedduration for a determination that the vehicle has been stationary.

Environmental component 124 may be configured to obtain currentenvironmental conditions, e.g., based on the current location of vehicle12. In some implementations, environmental conditions may includeweather conditions. In some implementations, environmental conditionsmay include visibility conditions. In some implementations,environmental conditions may include traffic conditions. Combinations ofmultiple different types of environmental conditions are envisionedwithin the scope of this disclosure, such as, by way of non-limitingexample, weather conditions, visibility conditions, and trafficconditions. In some implementations, environmental conditions mayinclude road-surface conditions such as wet, dry, icy, and/or otherconditions for the surface(s) of one or more particular roads. In someimplementations, certain determinations in system 100 may be based, atleast in part, on obtained environmental conditions. For example, aproximity threshold of 30 feet may be increased to 40 feet responsive topoor visibility conditions.

Interface component 126 may be configured to generate, effectuate,and/or present user interfaces to users, including but not limited tovehicle operators, vehicle owners, fleet managers, and/or otherstakeholders. In some implementations, notifications may be providedthrough one or more user interfaces in one or more vehicles. In someimplementations, interface component 126 may be configured to present aparticular user interface on a particular client computing platform to aparticular user. In some implementations, a user interface may includeone or more controllers, joysticks, track pad, a touch screen, a keypad,touch sensitive and/or physical buttons, switches, a keyboard, knobs,levers, a display, speakers, a microphone, an indicator light, aprinter, and/or other interface devices. User interfaces may beconfigured to facilitate interaction between users and system 100,including but not limited to receiving user input from users. In someimplementations, received user input may, e.g., be used to select whichdeterminations are to be used for vehicle event detection. In someimplementations, received user input may, e.g., be used to select aparticular proximity to be used for determinations by proximitycomponent 114 and/or another component of system 100.

In some implementations, server(s) 102, client computing platform(s)104, and/or external resources 128 may be operatively linked via one ormore electronic communication links. For example, such electroniccommunication links may be established, at least in part, via one ormore network(s) 13 such as the Internet and/or other networks. It willbe appreciated that this is not intended to be limiting, and that thescope of this disclosure includes implementations in which server(s)102, client computing platform(s) 104, and/or external resources 128 maybe operatively linked via some other communication media.

A given client computing platform 104 may include one or more processorsconfigured to execute computer program components. The computer programcomponents may be configured to enable an expert or user associated withthe given client computing platform 104 to interface with system 100and/or external resources 128, and/or provide other functionalityattributed herein to client computing platform(s) 104. By way ofnon-limiting example, the given client computing platform 104 mayinclude one or more of a desktop computer, a laptop computer, a handheldcomputer, a tablet computing platform, a NetBook, a Smartphone, a gamingconsole, and/or other computing platforms.

External resources 128 may include sources of information outside ofsystem 100, external entities participating with system 100, and/orother resources. In some implementations, some or all of thefunctionality attributed herein to external resources 128 may beprovided by resources included in system 100.

Remote computing server 129 may be separate, discrete, and/or distinctfrom individual vehicles (such as vehicle 12), and/or system 100. Insome implementations, remote computing server 129 may be configured toreceive, analyze, and/or otherwise process information from one of morevehicles, including but not limited to vehicle 12. In someimplementations, remote computing server 129 may be configured toreceive notifications from vehicle 12.

Server(s) 102 may include electronic storage 130, one or more processors132, and/or other components. Server(s) 102 may include communicationlines, or ports to enable the exchange of information with a networkand/or other computing platforms. Illustration of server(s) 102 in FIG.1 is not intended to be limiting. Server(s) 102 may include a pluralityof hardware, software, and/or firmware components operating together toprovide the functionality attributed herein to server(s) 102. Forexample, server(s) 102 may be implemented by a cloud of computingplatforms operating together as server(s) 102.

Electronic storage 130 may comprise non-transitory storage media thatelectronically stores information. The electronic storage media ofelectronic storage 130 may include one or both of system storage that isprovided integrally (i.e., substantially non-removable) with server(s)102 and/or removable storage that is removably connectable to server(s)102 via, for example, a port (e.g., a USB port, a firewire port, etc.)or a drive (e.g., a disk drive, etc.). Electronic storage 130 mayinclude one or more of optically readable storage media (e.g., opticaldisks, etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 130 may include one or more virtual storageresources (e.g., cloud storage, a virtual private network, and/or othervirtual storage resources). Electronic storage 130 may store softwarealgorithms, information determined by processor(s) 132, informationreceived from server(s) 102, information received from client computingplatform(s) 104, and/or other information that enables server(s) 102 tofunction as described herein.

Processor(s) 132 may be configured to provide information processingcapabilities in server(s) 102. As such, processor(s) 132 may include oneor more of a digital processor, an analog processor, a digital circuitdesigned to process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information. Although processor(s) 132 is shown in FIG. 1 asa single entity, this is for illustrative purposes only. In someimplementations, processor(s) 132 may include a plurality of processingunits. These processing units may be physically located within the samedevice, or processor(s) 132 may represent processing functionality of aplurality of devices operating in coordination. Processor(s) 132 may beconfigured to execute components 110, 112, 114, 116, 118, 120, 122, 124,and/or 126, and/or other components. Processor(s) 132 may be configuredto execute components 110, 112, 114, 116, 118, 120, 122, 124, and/or126, and/or other components by software; hardware; firmware; somecombination of software, hardware, and/or firmware; and/or othermechanisms for configuring processing capabilities on processor(s) 132.As used herein, the term “component” may refer to any component or setof components that perform the functionality attributed to thecomponent. This may include one or more physical processors duringexecution of processor readable instructions, the processor readableinstructions, circuitry, hardware, storage media, or any othercomponents.

It should be appreciated that although components 110, 112, 114, 116,118, 120, 122, 124, and/or 126 are illustrated in FIG. 1 as beingimplemented within a single processing unit, in implementations in whichprocessor(s) 132 includes multiple processing units, one or more ofcomponents 110, 112, 114, 116, 118, 120, 122, 124, and/or 126 may beimplemented remotely from the other components. The description of thefunctionality provided by the different components 110, 112, 114, 116,118, 120, 122, 124, and/or 126 described below is for illustrativepurposes, and is not intended to be limiting, as any of components 110,112, 114, 116, 118, 120, 122, 124, and/or 126 may provide more or lessfunctionality than is described. For example, one or more of components110, 112, 114, 116, 118, 120, 122, 124, and/or 126 may be eliminated,and some or all of its functionality may be provided by other ones ofcomponents 110, 112, 114, 116, 118, 120, 122, 124, and/or 126. Asanother example, processor(s) 132 may be configured to execute one ormore additional components that may perform some or all of thefunctionality attributed below to one of components 110, 112, 114, 116,118, 120, 122, 124, and/or 126.

FIG. 2 illustrates a method 200 for detecting a sitting duck scenario ofa vehicle on or near a road, in accordance with one or moreimplementations. The operations of method 200 presented below areintended to be illustrative. In some implementations, method 200 may beaccomplished with one or more additional operations not described,and/or without one or more of the operations discussed. Additionally,the order in which the operations of method 200 are illustrated in FIG.2 and described below is not intended to be limiting.

In some implementations, method 200 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 200 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 200.

At an operation 202, output signals are generated that conveyinformation pertaining to a particular vehicle and to the operation ofthe particular vehicle. Operation 202 may be performed by one or moresensors that are the same as or similar to set of sensors 108, inaccordance with one or more implementations.

At an operation 204, a current speed of the vehicle is determined basedon the output signals. In some embodiments, operation 204 is performedby a parameter determination component the same as or similar toparameter determination component 110 (shown in FIG. 1 and describedherein).

At an operation 206, a current location of the vehicle is determinedbased on the output signals. In some embodiments, operation 206 isperformed by a parameter determination component the same as or similarto parameter determination component 110 (shown in FIG. 1 and describedherein).

At an operation 208, road-specific information is obtained for one ormore roads near the current location of the vehicle. The road-specificinformation includes one or more types of road pertaining to the one ormore roads near the current location of the vehicle, and one or moretypes of geographical location information pertaining to the one or moreroads. In some embodiments, operation 208 is performed by aroad-specific information component the same as or similar toroad-specific information component 112 (shown in FIG. 1 and describedherein).

At an operation 210, a first determination is made whether the currentlocation of the vehicle is on or within a particular proximity ofhighways. The highways are public roads heading in one or moredirections, having one or more traffic lanes heading in the one or moredirections. The one or more traffic lanes are intended to includevehicular traffic. The first determination is based on the currentlocation and the obtained road-specific information. The particularproximity is determined based on a distance threshold. In someembodiments, operation 210 is performed by a proximity component thesame as or similar to proximity component 114 (shown in FIG. 1 anddescribed herein). In some implementations, the distance threshold maybe 100 feet or less. In some implementations, the distance threshold mayvary based on one or more of road type, environmental conditions, and/orother factors.

At an operation 212, a second determination is made whether the vehiclehas been stationary continuously for at least a specified duration. Insome embodiments, operation 212 is performed by a stationary componentthe same as or similar to stationary component 116 (shown in FIG. 1 anddescribed herein). In some implementations, the specified duration maybe at least 5 minutes. In some implementations, the specified durationmay vary based on one or more of road type, environmental conditions,and/or other factors.

At an operation 214, an occurrence is detected of a particular vehicleevent responsive to a combination of at least two determinations. The atleast two determinations include the first determination that thecurrent location of the vehicle is on or within the particular proximityof highways and the second determination that the vehicle has beenstationary continuously for at least the specified duration. In someembodiments, operation 214 is performed by a detection component thesame as or similar to detection component 118 (shown in FIG. 1 anddescribed herein).

At an operation 216, responsive to detection of the occurrence of theparticular vehicle event, one or more notifications are generatedregarding the particular vehicle event. In some embodiments, operation216 is performed by a notification component the same as or similar tonotification component 120 (shown in FIG. 1 and described herein).

At an operation 218, the one or more notifications are provided to oneor more of the vehicle operator and/or a remote computing server (e.g.,remote computing server 129). In some embodiments, operation 218 isperformed by a notification component the same as or similar tonotification component 120 (shown in FIG. 1 and described herein).

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present technology contemplates that, to theextent possible, one or more features of any implementation can becombined with one or more features of any other implementation.

1. A system configured for detecting a sitting duck scenario of avehicle on or near a road, the vehicle being operated by a vehicleoperator, the system comprising: a remote computing server including oneor more hardware processors, wherein the remote computing server isseparate and discrete from the vehicle, wherein the one or more hardwareprocessors are configured by machine-readable instructions to: receivevehicle-specific information pertaining to the vehicle and to operationof the vehicle, wherein the vehicle-specific information includes acurrent location of the vehicle and speed information for the vehicle;obtain road-specific information for one or more roads near the currentlocation of the vehicle, wherein the road-specific information includesone or more of: (i) one or more speed limits pertaining to the one ormore roads near the current location of the vehicle, and/or (ii) one ormore road types for the one or more roads near the current location ofthe vehicle, and/or (iii) one or more types of geographical locationinformation pertaining to the one or more roads; make a firstdetermination whether the current location of the vehicle is on orwithin a particular proximity of at least one road that has a speedlimit matching or exceeding 40 mph, wherein the first determination isbased on the current location of the vehicle and the obtainedroad-specific information; make a second determination whether thevehicle has been stationary continuously for at least a specifiedduration, wherein the second determination is based on thevehicle-specific information; detect an occurrence of a sitting duckevent responsive to a combination of at least two determinations,wherein the at least two determinations include the first determinationand the second determination; responsive to detection of the occurrenceof the sitting duck event, perform at least one of the following: (i)generate a first notification regarding the sitting duck event; and (ii)provide one or more notifications to at least one of the vehicleoperator and/or a remote user of the remote computing server.
 2. Thesystem of claim 1, wherein the particular proximity is determined basedon a distance threshold, and wherein the distance threshold is 100 feetor less, wherein the specified duration is at least 5 minutes, andwherein the one or more hardware processors included in the remotecomputing server are further configured by machine-readable instructionsto: make a third determination whether the vehicle is in one of a set ofdesignated areas for stopping vehicles; wherein detection of theoccurrence of the sitting duck event is further responsive to the thirddetermination that the vehicle is not in one of the set of designatedareas for stopping vehicles.
 3. The system of claim 1, wherein the oneor more hardware processors included in the remote computing server arefurther configured by machine-readable instructions to: make a fourthdetermination whether the vehicle is stationary in an orientationparallel to the particular road; wherein the detection of the occurrenceof the particular vehicle event is further responsive to the fourthdetermination that the vehicle is stationary in the orientation parallelto the particular road.
 4. The system of claim 2, wherein the set ofdesignated areas for stopping vehicles includes rest stops and travelcenters.
 5. The system of claim 4, wherein the set of designated areasfor stopping vehicles further includes common stop areas that have beenidentified based on historical vehicle usage.
 6. The system of claim 1,wherein the first determination includes a determination whether anypart of the vehicle is within a specified minimum distance of any partof a highway having one or more traffic lanes heading in oppositedirections, wherein the specified minimum distance is at least 25 feet.7. The system of claim 1, wherein the one or more hardware processorsincluded in the remote computing server are further configured bymachine-readable instructions to: determine whether the vehicle wastraveling at least 50 mph for at least 5 minutes in a particular timeframe, wherein the particular time frame includes a duration of at least10 minutes immediately preceding the specified duration for the seconddetermination that the vehicle has been stationary.
 8. The system ofclaim 1, wherein determining the current location of the vehicleincludes determining a current road selected from the one or more roadssuch that the current road is closer to the current location of thevehicle than other roads in the one or more roads, wherein the currentroad has a centerline between traffic lanes heading in oppositedirections, wherein the combination of at least two determinationsincludes a determination that the vehicle is stationary in anorientation parallel to the current road, and wherein the firstdetermination is that the current location of the vehicle is within 50feet of the centerline of the current road.
 9. The system of claim 1,wherein the one or more hardware processors included in the remotecomputing server are further configured by machine-readable instructionsto: obtain current weather conditions based on the current location ofthe vehicle, wherein the distance threshold used to determine theparticular proximity varies based on the current weather conditions. 10.The system of claim 1, wherein the distance threshold used to determinethe particular proximity varies based on one or more of (i) a particulartype of a road closest to the current location of the vehicle, (ii) aparticular type of the obtained geographical location information, (iii)how many traffic lanes are heading in a same direction as the vehicle atthe current location of the vehicle, (iv) how many traffic lanes formthe road closest to at the current location of the vehicle, and (v) aspeed limit for the road closest to at the current location of thevehicle.
 11. A method for detecting a sitting duck scenario of a vehicleon or near a road, the vehicle being operated by a vehicle operator, themethod comprising: receiving vehicle-specific information pertaining tothe vehicle and to operation of the vehicle, wherein thevehicle-specific information includes a current location of the vehicleand speed information for the vehicle; obtaining road-specificinformation for one or more roads near the current location of thevehicle, wherein the road-specific information includes one or more of:(i) one or more speed limits pertaining to the one or more roads nearthe current location of the vehicle, (ii) one or more road types for theone or more roads near the current location of the vehicle, and/or (iii)one or more types of geographical location information pertaining to theone or more roads; making a first determination whether the currentlocation of the vehicle is on or within a particular proximity of atleast one road that has a speed limit matching or exceeding 40 mph,wherein the first determination is based on the current location and theobtained road-specific information, and wherein the particular proximityis determined based on a distance threshold; making a seconddetermination whether the vehicle has been stationary continuously forat least a specified duration, wherein the second determination is basedon the vehicle-specific information; detecting an occurrence of asitting duck event responsive to a combination of at least twodeterminations, wherein the at least two determinations include thefirst determination and the second determination; and responsive todetection of the occurrence of the sitting duck event, performing atleast one of the following: (i) generating a first notificationregarding the sitting duck event; and (ii) providing one or morenotifications to at least one of the vehicle operator and/or a remoteuser of the remote computing server.
 12. (canceled)
 13. (canceled) 14.(canceled)
 15. (canceled)
 16. (canceled)
 17. (canceled)
 18. (canceled)19. (canceled)
 20. (canceled)